Enhanced network adapter framework

ABSTRACT

An enhanced network adapter framework, in which parameters are stored in a configuration table, the parameters being customized for a network and an application. A network adapter customized for the network and the application is instantiated based on invoking a generic network adapter which externally references the configuration table, and communication between the application and the network is effected using the instantiated network adapter.

FIELD

The present disclosure generally relates to custom network adapters.

BACKGROUND

One approach for creating a custom network adapter for effectingcommunication between a particular application and network is tohard-code the various communication parameters for the network adapterinto the network adapter's software, (e.g., JAVA, C, C++, Ada, Assemblycode or other software). If a second custom network adapter is needed,for instance if a different application or network are substituted, thesoftware code of the initial network adapter would have to be re-codedin some way in order to change its communication parameters.

SUMMARY

According to one general implementation, a generic network adapterincludes external references within its code to parameter tables. Customnetwork adapters, such as network adapters used with the TELCORDIA®ACTIVATOR or other applications, may be created by adjusting theparameter tables using, for example, a Structured Query Language (SQL)editor (e.g., TOAD, PL/SQL Developer, etc.), a straightforward table ortext editor, or any other editor. In doing so, less revision of actualsoftware, such as JAVA code, is required, reducing the need to store andmaintain multiple different software components (e.g., JAVA componentsor other software components) for each particular network configuration.For example, solutions for systems using generic network adapters canuse any suitable software, such as JAVA, C, C++, Ada, Assembly, etc.)

Among others, the one or more parameter tables may include a firstparameter table which maps each service to the multiple commandsrequired to implement that service; a second table which, using regularexpressions, maps messages returned from the network to unique messageidentifiers that are capable of being understood by the application ornetwork adapter framework; a third table which determines commandoutcomes based on the unique message identifier and the input command;and a fourth table which includes an eXtensible Markup Language (XML)template for each command outcome which is used to generate responsemessages that may be communicated to the application.

According to another general implementation, a computer-implementedprocess includes storing parameters in one or more configuration tables,the parameters being customized for a network and an application, andinstantiating a network adapter customized for the network and theapplication by invoking a generic network adapter which externallyreferences the one or more configuration tables. The process alsoincludes effecting communication between the application and the networkusing the instantiated network adapter.

Implementations may include one or more of the following features. Forinstance, effecting communication between the application and thenetwork using the instantiated network adapter may further includereceiving a request from the application to perform a service on thenetwork, identifying commands and a sequence of the commands associatedwith the service based on referencing a unique identifier of the servicein a first configuration table, transmitting a command, in sequence, tothe network, receiving a response to the command from the network,identifying a unique message identifier associated with the responsebased on executing regular expressions listed in a second configurationtable, and determining an outcome of the command based on referencingthe unique message identifier associated with the response and a uniqueidentifier of the command in a third configuration table.

In other examples, effecting communication between the application andthe network using the instantiated network adapter may further includedetermining an outcome of the service based on determining outcomes ofall commands associated with the service, selecting an XML returnmessage, including General Adapter Declarative Expression (GADE)variables, based on referencing the outcome of the service in a fourthconfiguration table, populating the GADE variables using one or moreresult values associated with the outcomes of all commands associatedwith the service, and providing the XML return message, populated withresult values, to the application.

In further examples, the service may be selected from an AsymmetricDigital Subscriber Line (ADSL) port disable service, an ADSL modifyparameters service, or an ADSL enable port service. An asymmetricdigital subscriber line is a digital subscriber line (DSL) where theupload speed may be different from the download speed. The regularexpressions for each possible response to the command may be listed withassociated unique message identifiers in the second configuration table.The second configuration table may list a catch-all regular expressionfor all previously unknown or unidentified responses sent by thenetwork, and a unique message identifier for the catch-all regularexpression. The outcome may identify whether the command was successfulor whether a fatal or non-fatal error has occurred, and whether rollbackis suppressed or not suppressed. The outcome may further identify aresult value. The application may be the TELCORDIA® ACTIVATOR or otherapplication.

In additional examples, the generic network adapter may be a JAVAEE-based network adapter. The parameters may include or describe valuesfor rules implementing process flows. The parameters include responsesthat may be expressed as regular expressions, and may include commandscapable of being sent from the application to the network, or responsesto the commands capable of being sent from the network to theapplication. The process may also include invoking the generic adapterusing a single configuration load of the one or more configurationtables, or detecting a type of the network and the application andselecting the one or more configuration tables from among a plurality ofconfiguration tables based on the detected type of the network and theapplication. The parameters may include actions associated with aloopback mode, a network emulator mode, and a network mode. Theparameters may include service definitions. The parameters includevalues that are included in XML requests generated by the Activator. Forexample, the values may be used to fill the GADE variables.

According to another general implementation, a system includes one ormore computers, and a computer-readable medium coupled to the one ormore computers having instructions stored thereon which, when executedby the one or more computers, cause the one or more computers to performoperations. The operations include storing parameters in one or moreconfiguration tables, the parameters being customized for a network andan application, instantiating a network adapter customized for thenetwork and the application by invoking a generic network adapter whichexternally references the one or more configuration tables, andeffecting communication between the application and the network usingthe instantiated network adapter.

Implementations may include one or more of the following features. Forexample, effecting communication between the application and the networkusing the instantiated network adapter further may further includereceiving a request from the application to perform a service on thenetwork, identifying commands and a sequence of the commands associatedwith the service based on referencing a unique identifier of the servicein a first configuration table, transmitting a command, in sequence, tothe network, receiving a response to the command from the network,identifying a unique message identifier associated with the responsebased on executing regular expressions listed in a second configurationtable, and determining an outcome of the command based on referencingthe unique message identifier associated with the response and a uniqueidentifier of the command in a third configuration table.

According to another general implementation, a computer storage mediumis encoded with a computer program, the program including instructionsthat when executed by data processing apparatus cause the dataprocessing apparatus to perform operations. The operations includestoring parameters in one or more configuration tables, the parametersbeing customized for a network and an application, instantiating anetwork adapter customized for the network and the application byinvoking a generic network adapter which externally references the oneor more configuration tables, and effecting communication between theapplication and the network using the instantiated network adapter.

The details of one or more implementations are set forth in theaccompanying drawings and the description, below. Other potentialfeatures and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a contextual diagram demonstrating a system forcreating network adapters using a network adapter framework.

FIG. 2 is a contextual diagram demonstrating a system for adaptingnetwork devices using a client device and a network adapter frameworkdevice.

FIG. 3 is a flowchart illustrating an example process for creatingnetwork adapters using a network adapter framework.

FIGS. 4 to 6 are block diagrams of exemplary network adapter frameworkarchitectures.

FIGS. 7 and 8 depict sample user interfaces that includes aconfiguration table and a table selection window for selecting aspecific configuration table for editing.

FIG. 9 is a contextual state diagram demonstrating states duringexecution of commands that are executed to create a network adapter.

FIG. 10 is a flowchart illustrating an example process for effectingcommunication between the application and the network using aninstantiated network adapter.

FIGS. 11 to 14 show other examples of configuration tables that may beused by the network adapter framework.

FIG. 15 shows an example translation of GADE variables into actualvalues in a return message.

FIG. 16 is a block diagram of exemplary computing devices that may beused to implement the network adapter framework.

In the various drawings, like reference numbers represent correspondingparts throughout.

DETAILED DESCRIPTION

According to the enhanced network adapter framework described herein, ageneric network adapter includes external references within its code toparameter tables. Custom network adapters, such as network adapters usedwith the TELCORDIA® ACTIVATOR or other applications, may be created byadjusting the parameter tables using, for example, a SQL editor (e.g.,TOAD, PUSOL Developer, etc.), a straightforward table or text editor, orany other editor. In doing so, little or no revision of actual software,such as JAVA code, is required, reducing the need to store and maintainmultiple different software components (e.g., JAVA components or othersoftware components) for each particular network configuration. Whilethis specification and the drawings provide examples using JAVA, JAVA EEand other specific software languages, any suitable software and/orsoftware languages can be used.

Among others, the parameter tables may include a first parameter tablewhich maps each service to multiple commands required to implement thatservice; a second table which, using regular expressions, maps messagesreturned from the network to unique message identifiers; a third tablewhich determines command outcomes based on the unique message identifierand the input command; and a fourth table which includes an XML templatefor each command outcome which is used to generate response messagesthat may be communicated to the application. In some implementations,the XML is generated after some or all of the commands associated withthe service have executed.

FIG. 1 is a contextual diagram of an exemplary system 100 for creatingnetwork adapters using a network adapter framework 102. Network adapterscreated using the system 100 provide network communications betweenapplications 104 and networks 106. For example, the applications 104, asdepicted, may include a TELCORDIA® ACTIVATOR application 104 a, a secondapplication (which may be, for example, a TELCORDIA® GRANITE INVENTORYapplication) 104 b, and a third application 104 c. The networks 106include networks 106 a, 106 b and 106 c. The system 100 may be used tocreate a network adapter or any other hardware or software componentconstructed and adapted to allow computers to communicate over acomputer network, such as a network card, a local area network (LAN)adapter, or a network interface card (NIC).

The system 100, using the network adapter framework 102, creates or“instantiates” network adapters that effect communication between theapplications 104 and the networks 106. For example, a particular networkadapter may be used for communication between the TELCORDIA® ACTIVATORapplication 104 a and the network 106 a. Other network adapters maysupport communications between the applications 104 b-c and the network106 c, between the TELCORDIA® ACTIVATOR application 104 a and thenetwork 106 c or between combinations of other applications andnetworks, whether depicted in FIG. 1 or not. “Instantiating” networkadapters refers to the creation of a customized network adapter byinvoking a generic network adapter which externally references aconfiguration table. The configuration table, which is described in moredetail later, stores data that may be used to customize a networkadapter for a particular network 106 and application 104. For example,for each type of device (e.g., Huawei, ZTE, Alcatel, etc.) there mayexist one or more adapters using the framework. When the Activatorrequests to execute a service (e.g., Create, Delete, etc.), it mayverify the kind of device, setting the identifier for the correctadapter in the XML request. For instance, if a CREATE request isgenerated for a ZTE device, the Activator may generate an XML requestfor the corresponding adapter and post it in the queue.

In some implementations, verifying the type of device and setting theidentifier for the correct adapter in the XML request can include thefollowing. When the TELCORDIA® ACTIVATOR needs to send a request for theadapter, it can read one or more configuration tables that identify thecorresponding network adapter that has to be used to execute theautomatic configuration for a particular network element. For example,the configuration tables can be database tables of the TELCORDIA®GRANITE INVENTORY application. In some implementations, a queue canexist that contains instances or entries, each of which is exclusive toa specific adapter. The entry can be, for example, a message driven bean(MDB) entry for that adapter. As such, each MDB entry can serve as aconsumer for that adapter in the queue. In any particular activatorrequest, the identifier of the adapter (e.g., a parameter in the messagethat identifies its “MDB consumer”) is unique so that each MDB entry isassociated with its correct requests.

The network adapter framework 102 includes a generic network adapter 108and a table selector 110. The generic network adapter 108 is operable toadapt an existing generic network adapter definition in order toinstantiate a new network adapter for a particular application 104 andnetwork 106. For example, if the network adapter framework 102 is beingused to create a network adapter for communication between theTELCORDIA® ACTIVATOR application 104 a and the network 106 a, thegeneric network adapter 108 may be used to select a generic networkadapter that is suitable (e.g., most closely matching) to instantiatethe specific network adapter needed. The network adapter framework 102may also use the table selector 110 to select and access tablesincluding configuration parameters used for instantiating a networkadapter to the specifications needed for a particular application 104and network 106. The generic network adapter 108 includes externalreferences 112 that are used to obtain specific parameters fromconfiguration tables.

The network adapter framework 102 may include one or more userinterfaces that may be used in defining new network adapters. Forexample, as depicted, the network adapter framework 102 includes a tableeditor interface 114, which may be part of a set of several screens on acomputer terminal or other interface for defining new network adapters.Similar interfaces 114 may exist to modify existing network adapters.

The table editor interface 114 includes a repository list 116. Forexample, the user who is using the table editor interface 114 to definenetwork adapters may select one of the entries (e.g., Services, Adapter,Messages, Parameters, Adapter, Results, etc.) from the repository list116. Some implementations of the table editor interface 114 may allowthe user to select tables in various ways. Depending on the user'sselection, a corresponding parameter table 115 may be displayed withinthe table editor interface 114. As depicted, the parameter table 115includes an ID column 118, a message column 120, a type column 122, anda value column 124. The user, while using the table editor 114 to definea network adapter for a specific application 104 and network 106, mayenter or modify values (e.g., AAFN-62) for an entry in the table, suchas “execute” entry 125 having a type 122 of “Error.”

In some implementations, the table editor interface 114 mayautomatically detect the type of the network and the application forwhich a network adapter is being defined. Using this information, thetable editor interface 114 may automatically select the configurationtable from among a group or list of configuration tables based on thedetected type of the network and the application.

The system 100 includes data stored on a computer-readable medium 126,where the data is used by the network adapter framework 102 and thetable editor interface 114 for creating network adapters (e.g., networkadapters 102 a-102 c) of the network adapter framework 102. The dataincludes network adapter framework data 128, Java Platform EnterpriseEdition (JAVA EE) code and run-time libraries 130, a parameterrepository 132, a table editor 134, and data tables 136. The networkadapter framework data 128 may include the code and data that supportthe execution of the computer software that makes up the network adapterframework 102. The tables 136 contain general fields associated withgeneric network adapter types. For example, one or more of the tables136 may represent generic network adapters comprising JAVA EE-basednetwork adapter information. Each of the tables 136 may be accessed bythe table editor interface 114. The parameter repository 132 includesparameters that may be used to customize general fields of the tables136 that represent generic network adapters when creating (orinstantiating) new network adapters. While this specification and thedrawings provide examples using JAVA, JAVA EE and other specificsoftware languages, any suitable software and/or software languages canbe used.

Parameters in the parameter repository 132 may include, for example,parameters corresponding to commands capable of being sent from theapplication 104 to the network 106, or responses to the commands capableof being sent from the network 106 to the application 104. In someimplementations, the parameter repository 132 may include parametersused, for example, as values for rules that implement process flows.

In some implementations, the parameter repository 132 may includeparameters associated with or that define actions associated with aloopback mode, a network emulator mode, and/or a network mode. In someimplementations, the parameter repository 132 may include parametersassociated with service definitions.

FIG. 2 is a contextual diagram demonstrating a system 200 for adaptingnetwork devices 202 using a client device 204 and a network adapterframework device 206. The client device 204 and the network adapterframework device 206 may be implemented in a single device that performsboth functions. The system 200 may be used for network frameworksadapted by the system 100 or other systems. The network devices 202include network devices 202 a through 202 d. The devices 204 and 206 maycommunicate with each other and with the network devices 202 using oneor more networks 208. Any of the networks 208, such as networks 208 aand 208 b, may be the Internet, a local area network (LAN), a wide areanetwork (WAN), a wireless network, a phone line, or other wired network,etc.

As depicted in FIG. 2, the client device 204 includes a storage medium210, an interface 212, a processor 214, a user interface 216 and aninput device 218. The storage medium 210 may store any of the data usedfor defining and/or configuring network adapters. The interface 212 mayhandle communications between the client device 204 and the networkadapter framework device 206. The processor 214 may perform the computerprocessing that the client device 204 uses to manage network adapters.The user interface 216 may provide the software interface that a user(e.g., a DSL provider technician, cable provider customer servicerepresentative, or other user) may use to interact with, and/or managedata for, the network adapter framework applications. For example, theuser interface 216 may include displays, menus, input fields, agraphical user interface, summaries, lists, etc. The input device 218may include one or more keyboards, a mouse, switches, buttons, or anyother controls that the user may employ to interact with the networkadapter framework applications, hardware, and firmware.

The storage medium 210 includes a table editor 220, tables 222, aparameter repository 224, and applications 226. The table editor 220includes the parameters and data used for presenting data tables to theuser for display and update. The tables 222 include the network adapterdata, such as relational database management system (RDBMS) tables(e.g., MS SQL server, DB2, Oracle, and MySQL) and/or flat files definingthe fields and values used in defining and configuring network adapters.The parameter repository 224 includes parameters that may be used tocustomize generic tables when creating (or instantiating) new networkadapters. The applications 226 may include one or more TELCORDIAActivator applications 228, JAVA EE 230 language and run-timeenvironments, and any other applications used for communicating with orconfiguring networks. For example, the TELCORDIA Activator applications228 may include any combination of TELCORDIA® ACTIVATOR and/or otherapplications.

As depicted, the network adapter framework device 206 includes aninterface 240 and storage medium 242. The interface 240 may handlecommunications between the client device 204 and the network adapterframework device 206. The interface 240 may also handle communicationsbetween the network adapter framework device 206 and the network devices202. The storage medium 242 includes a generic network adapter 244 and atable selector 246. The generic network adapter 244 is operable to adaptan existing generic network adapter definition in order to instantiate anew network adapter for a particular application 226 and network device202.

For example, if the network adapter framework device 206 is being usedto create a network adapter for communication between the TELCORDIA®ACTIVATOR application 228 and the network device 202 a, the genericnetwork adapter 244 may be used to select a generic network adapter thatis suitable (e.g., most closely matching) to instantiate the specificnetwork adapter needed. The network adapter framework device 206 mayalso use the table selector 246 to select and access tables containingconfiguration parameters used for instantiating a network adapter to thespecifications needed for a particular application 226 and networkdevice 202. The generic network adapter 244 includes external references248 that are used to obtain specific parameters from configurationtables, such as from remote locations through the Internet. For example,for each type of device (e.g., Huawei, ZTE, Alcatel, etc.) there mayexist one or more adapters using the framework. When the Activatorrequests to execute a service (e.g., Create, Delete, etc.), it mayverify the kind of device, setting the identifier for the correctadapter in the XML request. For instance, if a CREATE request isgenerated for a ZTE device, the Activator may generate an XML requestfor the corresponding adapter and post it in the queue.

As depicted, the network device 202 a includes services 254, a processor256, storage medium 258, and an interface 260. The services 254 mayinclude commands and parameters for establishing network services (e.g.,DSL provisioning services, cable provider services, etc.) on the networkdevice 202 a, such as connecting or configuring DSL, changing DSLsettings (e.g., transfer rates, etc.) or disconnecting DSL services. Theprocessor 256 may perform the computer processing that the networkdevice 202 a uses to provide services. The medium 258 may store the dataneeded for execution by the network device 202 a. The interface 260 mayhandle communications between the network device 202 a and variousnetwork equipment 252 a-252 b. For example, equipment 252 a-252 b mayinclude DSL modems, gateways, or other hardware or equipment thatprovides or import services.

FIG. 3 is a flowchart illustrating an example process 300 for creatingnetwork adapters using a network adapter framework. For example, theprocess 300 may be a computer-implemented method used within the networkadapter frameworks of systems 100 and 200. Briefly, the process includesstoring parameters in one or more configuration tables, the parametersbeing customized for a network and an application, and instantiating anetwork adapter customized for the network and the application byinvoking a generic network adapter which externally references the oneor more configuration tables. The process also includes effectingcommunication between the application and the network using theinstantiated network adapter.

In more detail, when the process 300 begins, parameters are stored inone or more configuration tables (operation 302). The parameters arecustomized for a network and an application. For example, referring toFIG. 2, a set of parameters, stored in the parameter repository 224, maybe used by the network adapter framework device 206 to create networkadapters on the network devices 202 a or any of the other networkdevices 202. The parameters may define commands and services that may beused for creating customized network adapters. The parameters may alsoinclude numeric settings used by applications, such as TELCORIDA®ACTIVATOR, to create network adapters. The parameters may furtherinclude status and message information associated with executing thecommands and services. For example, referring to FIG. 1, the parametertable 115 includes the ID column 118, the message column 120, the typecolumn 122, and the value column 124, all of which may define messagesassociated with specific commands and services. In some implementations,the adapter may read the configuration data (stored in the tables or adatabase) prior to starting the adapter in the server (e.g., deployedthe generic network adapter 244).

A network adapter is instantiated that is customized for the network andthe application (operation 304). The instantiation is based on invokinga generic network adapter which externally references the one or moreconfiguration tables. For example, referring to FIG. 1, the networkadapter framework 102 may use tables such as table 115 to create acustomized network adapter for any of the networks 106 a through 106 c.The customized network adapter created is device- andapplication-specific. For example, the device specificity may depend onthe particular hardware device (e.g., a specific DSL modem or otherpiece of hardware). The application specificity may depend on thespecific application 104 being executed, e.g., the TELCORDIA® ACTIVATORapplication 104 a, the TELCORDIA® GRANITE INVENTORY application 104 b,or any other generic application 104 c.

Communication is effected between the application and the network usingthe instantiated network adapter (operation 306), thereby ending process300. For example, using the newly-instantiated network adapter, thespecific application 104 may communicate with the specific network 106for which the network adapter was created and customized.

FIG. 4 is a block diagram of an exemplary architecture 400 for providinga network adapter framework. For example, the architecture 400 may beused for the systems 100 and 200. The architecture 400 may facilitatethe creation of a network adapter 402 by any network adapterapplication, such as a TELCORDIA® ACTIVATOR application 404.

The network adapter 402 includes application development software and amiddleware or other messaging service, such as a JAVA message services(JMS) 406, an activator interface 408, several configuration tables andprotocols in a network adapter framework 410, and a connection manager412. The network adapter 402 may be configured, for example, to handleTransaction Language 1 (TL1) protocols or other telecommunicationsprotocols for DSL Access Multiplexer (DSLAM) scope. Using configurationtables may provide the advantage of flexibility, for example, throughthe use of regular expressions to analyze network commands, parametersand responses. Configuration table information (e.g., commands,messages, rules, regular expressions, etc.) used by the network adapterframework 410 may allow network adapters to be created without changingcode in applications such as the TELCORDIA® ACTIVATOR application 404.

In some implementations, the TELCORDIA® ACTIVATOR application 404 mayinterface with the network adapter 402 using eXtensible Markup Language(XML) commands and responses 414. The XML commands and responses 414 maybe managed using queues or other processes for managing messages,commands and communications. For example, an input queue may handleservice requests (e.g., activate DSL, cancel DSL, etc.) that are issuedby the TELCORDIA® ACTIVATOR application 404.

XML commands and responses 414 may be handled by the applicationdevelopment software and JMS Queue interface 406 and sent to (orreceived from) the activator interface 408. For example, the activatorinterface 408 may include activator flow commands 416 that may be usedto execute the services requested by the TELCORDIA® ACTIVATORapplication 404. Similarly, responses that result from executing thecommands may be sent by the activator interface 408 to an output queuemanaged by the application development software and JMS interface 406.

The network adapter framework 410 may include protocols, adapter tablesand information, flow control commands (e.g., process a service,rollback a command if a service fails, etc.) and a communicationcontroller. The network adapter framework 410 may communicate with theconnection manager 412 through a communication wrapper 418. Theconnection manager 412 may communicate with network devices andequipment (e.g., DSL modems or other equipment) using a communicationfacade 420. The communication may occur over a network 422, such as theInternet, a local area network (LAN), a wide area network (WAN), awireless network, a phone line or other wired network, etc. In someimplementations, the protocols included by the network adapter framework410 can be standardized protocols such as Common Object RequestingBroker Architecture (CORBA), Common Management Information Protocol(CMIP), Transaction Language 1 (TL1), or other communications protocols,etc.

FIG. 5 is a block diagram of another exemplary architecture 500 for anetwork adapter framework. For example, the architecture 500 may be usedwithin the systems 100 and 200. The architecture 500 includes an adapterarchitecture activator interface 502 and an adapter frameworkarchitecture 504. The adapter architecture activator interface 502 mayinclude a message driver bean for handling messages and an interface forcommunicating with the adapter framework.

The adapter framework architecture 504 includes generic executionclasses, a services commands definition layer 506, command pre-processutilities, generic communication parameters, and a connection manager.The services commands definition layer 506 may include adapterinformation, service group information, services, commands, parameters,messages, responses and return messages. These components of theservices commands definition layer 506 may be organized, for example, ina series of configuration tables for use in creating customized networkadapters for specific application and network devices.

In some implementations, generic execution classes can include Javaclasses that implement the common logic to process the requests. Forexample, the Java classes can include: INTEGRA.ADAPTER.COMM.LOG,INTEGRA.ADAPTER.COMM.TL1.ERROR, INTEGRA.ADAPTER.COMM.TL1.ERROR,INTEGRA.ADAPTER.CORE, INTEGRA.ADAPTER.FRWK.ADAPTERINTERFACE,INTEGRA.ADAPTER.FRWK.BEAN, INTEGRA.ADAPTER.FRWK.COMM,INTEGRA.ADAPTER.FRWK.ERROR, INTEGRA.ADAPTER.FRWK.GADE,INTEGRA.ADAPTER.FRWK.LOG, INTEGRA.ADAPTER.FRWK.UTIL,INTEGRA.ADAPTER.UTILS, other INTEGRA.ADAPTER classes or subclasses, orother classes. The services commands definition layer 506 can, forexample, enable services that are mapped to the instances of thecorresponding adapters.

Command pre-process utilities can be composed mainly of macro classutilities, gathering the necessary features for the correctinterpretation and compilation of GADE expressions. The macro classutilities can identify and separate the parts of the expressionsthemselves, such as the GADE part of the regular expression that ispure. At the time of compilation, these data can be organized internallyto ensure better performance in processing the specific attributes ofthe GADE language.

Generic communication parameters can represent the layer of specificcommunication with the network through the design of the call and theconcept of the command. This allows each command to run as an atomicunit, synchronously, as a request/response pair, driven by the interfacedefined. This interface, for example, can be implemented specificallyfor a session bean, providing features for managing connections andimplementation of controls according to the needs of the network adapterframework. The main features defined by this interface can include: 1)requests for a connection independent of the technology used incommunication with the network; 2) requests for command execution in thenetwork standard; and 3) requests for the closure of the operation,allowing the release of the connection.

The connection manager can be responsible for managing the connectionsbetween and network adapters in order to provide connections on demandto the adapters. To initialize the connection manager, a set ofconnections can be created (e.g., to initiate the request forconnection) and be available to the requests of adapters. Eachconnection request can be used, then returned to the connection manager(e.g., to be used in another request, if necessary).

In some implementations, (e.g., in a loopback mode or if the networkemulator is active), the command may not be sent via the network.Instead, the answer can be obtained from a configuration file.

In some implementations, for each adapter instance, there can be aninstance of communication façade 420 and the communication connectionhandler.

In some implementations, a connection manager can exist for each networkmanagement system, such as to provide better availability in certainsettings within the network. In this way, the failure of a singleconnection manager cannot cause the loss of access by all networkmanagement systems concerned. Moreover, having multiple connectionmanagers can prevent loss of access when maintenance is programmed in,or scheduled for, a single connection manager.

In some implementations, examples of which are discussed in more detailbelow with respect to FIGS. 11-15, the services commands definitionlayer 506 may include rules associated with the services, mapped inseveral database tables. At start-up of the network adapter framework,for example, all of the information from the database tables may beloaded into virtual memory. Having one initial load of configurationdata per execution may help to reduce database performance or accessvolume problems.

In some implementations, the services commands definition layer 506 mayfurther provide: table-defined configuration of commands and commandparameters; recursive command parameterization; command level retryparameterization tailored accordingly for each possible network returnmessage; rollback mapping customized to the network return messages foreach command executed; command flow mapping, including conditionalrules; network result messages parameterization, mapping andclassification; parameterization of network exception handling rules;and command specific timeout parameterization.

FIG. 6 is a block diagram demonstrating another exemplary architecture600 for a network adapter framework. For example, the architecture 600may be used for the systems 100 and 200. The architecture 600 includesan activator adapter 602, a discovery adapter 604, an adapter connectionmanager 606, a discovery connection manager 608, a network managementsystem (NMS) 610, and a network 612.

The activator adapter 602 and the discovery adapter 604 can be used bythe framework to connect and send the commands to the network throughthe connection manager. The adapter connection manager 606 and thediscovery connection manager 608 can include and/or use applicationsthat send and receive commands to and from the adapter. In someimplementations, the connection managers 606 and 608 may not handle theactivation rules, but rather the managers 606 and 608 may operate byreceiving commands that are to be sent through the network (e.g., viathe NMS 610). The NMS 610 can be responsible for controlling andmanaging the commands, such as configuration commands and systemcommands, and for sending the commands to the network elements. The NMS610 can be a part of the network, but in some implementations may beoptional.

The activator adapter 602 and the discovery adapter 604 can be differenttypes of systems. For example, the activator adapter 602 can be aTELCORDIA® system that automatically configures the network. Thediscovery adapter 604 can be, for example, a TELCORDIA® system thatautomatically discovers or determines the configuration of the networkelements in the network. Both adapters 602 and 604 can send commands andhandle responses, but with different business or technical objectives.

FIG. 7 shows a sample user interface 700 that includes a configurationtable 702 and a table selection window 704 for selecting a specificconfiguration table for editing. For example, using applications thatare invoked as part of a network adapter framework (e.g., of systems 100and 200), the user may select from a table list 706 for editing. In someimplementations, the tables listed in the table list 706 may all have acommon prefix (e.g., “TB_”) indicating that the entries in the list aretable names. Other non-table entities that appear in other lists mayhave other prefixes if they are not tables, such as parameters,variables, or other entities.

In one example using the user interface 700, if the user selects thecommand table entry 708 (e.g., “TB_COMMAND”) from the table list 706,the configuration table 702 may be displayed. In this case, theconfiguration table 702 may contain information related to networkadapter commands, including column headings 710 for the command ID, amessage ID, a message number, a suppress rollback flag, a messagesubtype, a message result type, a message result code, and a messagedescription.

In some implementations, controls may exist for optimizing orreorganizing the display of information. For example, sort controls 712or other controls may allow the user to arrange the information in amore convenient way (e.g., sorted by message subtype, etc.).

A row 714 in the sample configuration table 702 may contain all of thefields associated with that entry. As depicted, the row 714 that ishighlighted lists a value of “ACT_CM_ZTE_(—)009” for the command ID,“ACT_MS_ZTE_(—)002” for the message ID, “Success” for the messagesubtype, and so on. As is the case for the sample configuration table700 and other configuration tables described herein, multiple rows mayhave common values for some of the columns or fields. For example, rows716, 718 and 720 each list “ACT_CM_ZTE_(—)009” for the command ID, buteach has a different message ID.

In some implementations, highlighting a row (e.g., the row 714) in aconfiguration table may allow the user to edit fields in the row, suchas the way that some common spreadsheet applications function. In someimplementations, highlighting a row may cause one or more windows,pop-ups or screens to appear in which the user may add, modify or deleteinformation. Other user interface 700 controls and capabilities may alsoexist, such as mouse selection and dragging, right button commands,radio buttons, checkboxes, or any other controls that are common ingraphical user interfaces (GUIs). In some implementations, a SQL editor(e.g., TOAD, PUSQL Developer, etc.) may be used to modify data in theconfiguration table 700.

FIG. 8 shows another sample user interface 800 that includes a sampleconfiguration table 802 and a data editing window 804 for editing data(e.g., command information) for a specific entry in the configurationtable 802. For example, the configuration table 802 may be displayed forediting command information if the user selects the command table entry708 from the table list 706. Moreover, the data editing window 804 maybe displayed when the user selects a specific row or cell in theconfiguration table 802.

For example, a first row 806 is selected in the configuration table 802as indicated by bolding around the row. As a result, the data editingwindow 804 contains the current values of data elements associated withthe row 806. For instance, a value entry box 808 contains the currentvalue (e.g., “LOGIN:::<INSERT_CTAG_HERE> . . . ”) corresponding to acell 810 in the “command expression” column 812 for that row 806. Therow 806, as depicted, represents the information for a command having“ACT_CM_HUA_(—)001” as the command ID, “LOGIN HUAWEI” as the commanddescription, “LOGIN:::<INSERT_CTAG_HERE> . . . ” as the commandexpression, and 5000 as the timeout threshold (e.g., how manymilliseconds to wait for the command to execute before raising a timeoutexception or error).

In some implementations, components of the command descriptionsurrounded by special characters, such as “<” and “>” in“<INSERT_CTAG_HERE>” may be a signal to the network adapter framework tosubstitute an actual value or parameter into the command expression.Parameters may be stored, for example, in other configuration tables notdescribed herein.

The user interface 802 may include multiple data entry fields, such as aline terminator field 814 having “Platform Defaulf” as the current value816. The user interface 800 may include buttons or other controls, suchas a change button 818 that may allow the user to modify the value ofthe line terminator field 814 or other fields. Additional controls 820may exist that allow the user to add rows in the configuration table802, to verify a change (e.g., using an “OK” button), or to cancel achange. The user interface 802 may also include other controls, such asa horizontal slider bar 822 and a vertical slider bar 824 that may beused, for example, for controlling the position of the display in thevalue entry box 808.

In some implementations, user interfaces employed in the network adapterframework may have hot-key or other shortcuts for selecting options,etc. For example, the line terminator field 814 and other fields mayhave an underlined character (e.g., “T” in “Terminator”) that indicatesthat a Alt-T, Ctrl-T or other key sequence may also be used to selectthe option.

FIG. 9 is a contextual state diagram 900 demonstrating the use of acustomized network adapter created with the enhanced network adapterframework, in various states. Specifically, the states 902 a through 902c pertain to the use of regular expressions, and the state 902 dpertains to the automatic generation of XML commands during use of thenetwork adapter framework.

The states 902 a through 902 c effect communication between theapplication and the network using the instantiated network adapter. Thestates 902 a through 902 c involve receiving a request from theapplication to perform a service on the network and identifying asequence of commands associated. The commands are transmitted insequence, each resulting in a response that is received. For eachresponse, regular expressions may be executed to deterministicallydetermine an outcome for the command. The regular expressions are basedupon unique message identifiers and/or patterns of messages.

The state 902 d also effects communication between the application andthe network using the instantiated network adapter. However, the endresult of the state 902 d is to provide an XML return message, populatedwith result values for each command in the sequence of commandsassociated with the service, to the application. The XML return messagemay include GADE variables, which are substitution variables embedded inreturn messages. The GADE variables are replaced with actual valuesprior to transmission to the application, depending on various factors.For example, GADE variables may be based on referencing the outcome ofthe service and the one or more result values associated with theservice. The GADE variables may also depend on entries in one or moreparameter tables. The outcomes of all commands associated with theservice may be used to determine the overall outcome of the serviceitself.

The states 902 involve communications between applications 904, networkadapter frameworks 906 and networks 908. The processing andcommunications in each state depend on the corresponding configurationtable 910 for that state. The configuration tables 910 shown here depictjust enough rows and columns to support a description of the examplestates 902. In some implementations, additional columns may exist,providing more robust functionality (e.g., rollbacks, time-outs, etc.),and other rows may exist representing additional services, commands,messages, etc.

In FIG. 9, although the applications 904 a through 904 d are consideredto be the same application, they are differentially labeled for ease ofreference when describing the separate states 902. The same is true forthe network adapter frameworks 906 and networks 908. Nevertheless, thestates 902 may be used by any combination of applications 904, networkadapter frameworks 906 and networks 908.

In the first state 902 a, the application 904 a identifies a service 912a (e.g., SVC_(—)01) to be performed by the network adapter framework 906a. “SVC_(—)01” identified by the service 912 a is listed in the firstcolumn of the configuration table 910 a. In this example, theconfiguration table 910 a is a “service-command” table, identifying thecommands and sequence of commands to be executed for any particularservice (e.g., SVC_(—)01). Examples of services represented by SVC_(—)01may include services for activating DSL, deactivating DSL, establishingsatellite TV service, connecting or configuring in-home peripherals(e.g., digital video recorders or DVRs), etc.

The network adapter framework 906 a uses the service 912 a (e.g.,SVC_(—)01) identified by the application 904 a to access theconfiguration table 910 a, looking up the one or more commandscorresponding to the service. In this case, the commands (e.g.,CMD_(—)01 through CMD_(—)03) are stored in the second column of theconfiguration table 910 a. In addition, the corresponding sequenceorders (e.g., 10, 20, 30) of the commands are found in the third columnof the configuration table 910 a. Using the first command (e.g.,CMD_(—)01) obtained from the configuration table 910 a, the networkadapter framework 906 a may send the first command 914 a (e.g.,“CMD_(—)01”) to the network 908 a where the command is executed.

The remaining commands corresponding to the service may also beexecuted, in sequence, with each execution resulting in some kind ofreturn status (e.g., “SUCCESS”, “ERROR,” “UNRECOGNIZED,” etc.). In thecurrent example, CMD_(—)02, having a sequence of 20 would be executedafter CMD_(—)01 having a sequence of 10. The third and last commandexecuted, CMD_(—)03, has the highest sequence order of 30.

In the second state 902 b, the network 908 b generates a return status914 b (e.g., “SUCCESS”), that results from executing the command. Thenetwork adapter framework 906 b may parse the return status 914 b (e.g.,“SUCCESS”) and access the configuration table 910 b to locate thematching table row that contains “SUCCESS”. In this case, the messagecode that corresponds to “SUCCESS” in configuration table 910 b isMS_(—)001.

In some implementations, the second state 902 b, including theconfiguration table 910 b, may be implemented using regular expressionsor any other formal language for defining and recognizing particulartext strings of interest. Using regular expressions, for example, mayallow predictable messages to be pre-loaded into a table, such as theconfiguration table 910 b, for comparison with actual return messagesreceived from network devices. This may provide a flexible anddeterministic way for identifying text strings of interest, such asparticular return or error messages, or patterns of words in messages.

In the third state 902 c, the network adapter framework 906 c combinesthe message code MS_(—)001 with the command code CMD_(—)01 to access theconfiguration table 910 c. In this case, the configuration table 910 ccontains four visible columns, the first two providing the “key” orlook-up indexes. The third column having the first-row entry “PASS” is astatus field. The fourth and last column (e.g., with entry “DSL OK”) isa result code field. As a result of accessing the configuration table910 c, the “MS_(—)001+CMD_(—)01” pair, for example, may result inlooking up a return status 914 c of “‘PASS’+‘DSL OK.’” The result code“DSL OK” may be passed to the application 904 c at this stage, or may beused later to populate an XML response message.

In the fourth state 902 d, the status results of a service's commandsmay be grouped together in order to generate a service-level resultmessage. For example, as a result of receiving the service 912 a (e.g.,SVC_(—)01) and executing the corresponding commands CMD_(—)01, CMD_(—)02and CMD_(—)03, the commands' status results 914 d (e.g., PASS, PASS andPASS) may be combined to access the configuration table 910 d. The firstcolumn in the configuration table 910 d may contain all possiblecombinations of results of separate commands executed in sequence for aparticular service. As depicted, the configuration table 910 d containsone row or entry, but other tables may be, for example, “PASS, PASS,FAIL,” “PASS, FAIL, N/A,” etc. As a result of looking up the entry for“PASS, PASS, PASS”, the entry in the table's second column (e.g.,“Process Response” +[RESULT_CODE]) may be found, meaning that the“process response” is to be concatenated with the [RESULT_CODE] from theconfiguration table 910 c. Upon making the substitution for the[RESULT_CODE], a service-level result 912 d (e.g., “Process Response—DSLOK”) may be generated and returned to the application 904 d. The result912 d may be formatted as an XML return message.

FIG. 10 is a flowchart illustrating an example process 1000 foreffecting communication between the application and the network using aninstantiated network adapter. The process 1000 may be used, for example,in combination with the process 300 described with regard to FIG. 3. Forexample, the process 1000 may be a computer-implemented method usedwithin the network adapter frameworks of systems 100 and 200. Moreover,referring to FIG. 9, the process 1000 may be used to perform theprocessing described with regard to states 902 a through 902 cpertaining to regular expressions and state 902 d pertaining togenerating and providing XML return messages.

A request is received from the application to perform a service on thenetwork (operation 1002). For example, referring to FIG. 2, the requestmay be a “Start DSL Service” service request issued by a user (i.e.cable provider customer service representative) of any of the TELCORDIAActivator applications 228. The client device 204 may send the servicerequest to the network adapter framework device 206.

Commands and a sequence of the commands associated with the service areidentified by referencing a unique identifier of the service for theclient device in a first configuration table (operation 1004). Forexample, based on the “Start DSL Service” service request received fromthe client device 204, the network adapter framework device 206 maydetermine the individual commands needed to effect the service. Thedetermination may be made, for example, by accessing tables 222 (e.g.,the configuration table 910 b or other such table), using the servicecode (e.g., SVC_(—)01) to obtain the corresponding commands. The firstconfiguration table lists the commands and sequence of commands to beexecuted for the unique identifier. In some implementations, uniqueidentifiers can be determined in the same way that primary keys areselected for a database, such as at configuration time (e.g., commandssuch as database CREATE TABLE commands).

Commands are transmitted, in sequence, to the network (operation 1006).For example, the network adapter framework device 206 may transmit thecommands, in sequence, to at least one of the network devices 202. Insome implementations, if several network devices 202 of the same typeare being configured with a network adapter, the commands may betransmitted to each network device 202, either serially or in parallel.In this way, it may be possible to create several network adapters atthe same time. Transmission of commands to the network devices 202 mayoccur over the one or more networks 208.

A response to the command is received from the network (operation 1008).For example, based on the execution of the command on the particularnetwork device 202, the network device 202 may transmit a response tothe network adapter framework device 206. The response may be in theform of a text string or other message.

A unique message identifier associated with the response is identifiedby executing regular expressions listed in a second configuration table(operation 1010). For example, client device 204 may access one of thetables 222, such as a configuration table containing regularexpressions, and generate a unique message identifier (e.g., MS_(—)001)that is associated with the response (e.g., “SUCCESS”). If no matchingmessage identifier can be determined, the client device 204 may use orgenerate a default message identifier.

An outcome of the command is determined by referencing the uniquemessage identifier associated with the response and a unique identifierof the command in a third configuration table (operation 1012). Forexample, the service code (e.g., SVC_(—)01) may be used in combinationwith the message identifier (e.g., MS_(—)001) in order to determine thecommand's outcome.

An outcome of the service is determined by determining outcomes of allcommands associated with the service (operation 1014). For example, ifthree commands are executed for the service, the outcomes of each of thecommands are considered as a group in determining the outcome of theservice itself. In one implementation, if the outcomes of the commandsare PASS, PASS and PASS, the three outcomes may be combined to access aconfiguration table (e.g., configuration table 910 d) to obtain, forexample, a process response and a result code.

An XML return message is selected, including GADE variables, byreferencing the outcome of the service in a fourth configuration table(operation 1016). For example, using the configuration table 910 d or asimilar table, the network framework may look up “ProcessResponse”+[RESULT_CODE] using the PASS, PASS, PASS result of theservice. In this example, [RESULT_CODE] may be a GADE variable.

The GADE variables are populated using one or more result valuesassociated with the outcomes of all commands associated with the service(operation 1018). For example, using the [RESULT_CODE] GADE variable,the framework may populate the message with DSL OK.

The XML return message is provided, populated with result values, to theapplication (operation 1020). For example, the network adapter framework906 d may return the response 912 d (e.g., “Process Response—DSL OK”) tothe application 904 d.

FIGS. 11 to 14 show more detailed examples of configuration tables thatmay be used by the network adapter framework within each of the systems100 and 200. Specifically, FIG. 11 shows an example service commandtable 1100. Each row or entry in the service command table 1100 maystore, for each service ID 1102, command IDs 1104 of the commands usedto perform the service, sequence numbers 1106, rollback services 1108,rollback enable indicators 1110, and conditional commands 1112. Theservice command table 1100 may be used for looking up the commands for aparticular service, as well as the command sequences, so that thecommands may be executed in the designated sequence order.

Conditional commands 1112 can include commands that are executed basedon one or more conditions defined for them. For example, consider aconditional command 1113 a such as“:#ACT_ALCATEL_CARD_MODEL:]”==“ADLT-L”∥“[:#ACTALCATEL_CARD_MODEL:]”==“ADLT-W”. When the framework executes, the valuesof the conditional commands 1112 column are generally translated andevaluated. For instance, the result of the evaluation of the conditionalcommand 1113 a can determine whether a “CM_(—)005” command 1113 b of an“SV_(—)007” service 1113 c (e.g., both on the same row as theconditional command 1113 a) is executed. In particular, if“ADLT-L==ADLT-L∥ADLT-L==ADLT-W” is TRUE, then the “CM_(—)005” command1113 b is executed. Otherwise, if the evaluation results in a FALSEresult, then the “CM_(—)005” command 1113 b is not executed.

FIG. 12 shows an example message table 1200. Each row or entry in themessage table 1200 may store a message ID 1202 and a correspondingmessage expression 1204. Each message ID 1202 may be a regularexpression that is capable of being executed in order to determine aunique message ID 1202 given a particular message description 1204. Themessage table 1200 may be used for determining the message ID for aparticular message.

FIG. 13 shows an example command message table 1300. Each row or entryin the message table 1300 may store a command ID 1302, a message ID1304, a message sequence 1306, a suppress rollback indicator 1308, amessage subtype 1310, a message result type 1312, a message code 1314,and a message description 1316. The command message table 1300 may beused to determine the values related to a value pair combining thecommand ID 1302 and the message ID 1304.

FIG. 14 shows an example return message table 1400. Each row or entry inthe return message table 1400 may store a return message ID 1402, areturn message description 1404, and a return message expression 1406.The return message table 1400 may be used to determine the returnmessage expression 1406 corresponding to a particular return message ID1402.

The detailed example that follows identifies one or more implementationsof how specific entries in the configuration tables 1100 through 1400may be used. When the adapter is started in the server (e.g., based on afile, such as AdapterConfiguration.xml), the adapter may read theconfiguration (stored in the tables or database) once, processing eachrequest in memory.

The Activator application, such as the TELCORDIA® ACTIVATOR application228, issues requests for a network to perform services. With regard toDSL, example services may include, for example, the CREATE, DELETE, andSUSPEND services. Each service is associated with a unique service ID,such as Service 1 1114 that has the value SV_(—)001 for the service ID1102, as defined in the configuration table 1100. In this example,SV_(—)001 occupies five rows in the service command table 1100 becausefive commands are used to execute the service. Other services in thetable are SV_(—)002 through SV_(—)007, each having various numbers ofrows, one row per command. In some implementations, to determine aunique service ID, the framework can use the adapter name, adapter modeland card model (e.g., all of which can be available in the XML request)to determine a group code. Using the group code and the operation name,the framework can uniquely determine the service to be executed.

A service, such as the CREATE service, may include one or more commandsthat are to be executed in sequence by the network in order to performthe service. Example commands may include, for example, LOGIN, PORTDISABLE ADSL, MODIFY PARAMETERS ADSL, ENABLE PORT ADSL, LOGOUT or otherAsymmetric Digital Subscriber Line (ADSL) commands. Each command isassociated with a unique command ID (e.g., any of the command IDs 1116ranging from CM_(—)001 through CM_(—)005). For each service, thecommands are executed in a sequence defined by the a sequence parameter1106 (e.g., values 10, 20, 30, 40 and 50 that make up the sequences1118). Using FIG. 11 as an example, Service 1 1114 includes commands 1,2, 3, 4 and 5 executed in sequence, Service 2 1120 includes commands1122 1, 2, 6 and 5 in sequence, and Service 3 1124 includes commands1126 1, 2, 3, 4 & 5 in sequence.

Depending upon the service that the command is being used to implement,the command may be associated with a roll-back procedure, as identifiedin the service rollback column 1108, to un-do the service if an error isencountered. For example, Command 1 of Service 1 has no associatedrollback procedure (e.g., as indicated by a “NULL” value 1128). Command4 of Service 3 is associated with rollback procedure #9 1130. Notably,this same command 4 is associated with a different rollback procedure #61132, when performed in association with service 5.

Thus, one purpose of the service command table 1100 is to identify anddesignate the sequence of commands to be performed by the network foreach service requested by the Activator application. The configurationtables, including the service command table 1100, may be loaded intomemory at the time that the adapter is first instantiated. Allprocessing may therefore occur within this memory.

In addition to the service command table 1100, the network adapterframework uses several other configuration tables to effectcommunication between the application and the network. The nextconfiguration table, called the message table 1200 (FIG. 12), listsregular expressions (e.g., in the message expression column 1204) forall possible responses sent by the network, including a “catch-all”regular expression parameter 1206 for unknown or unidentified responses.Specifically, the “catch-all” regular expression parameter 1206 is aperiod, and the corresponding “catch-all” message ID 1208 is MS_(—)031,as shown by table row 1210. Each possible response listed in the messageexpression column 1204 is associated with a unique message ID 1202. Iffor some reason the “catch-all” message ID 1208 is used significantlyoften for the same undefined message expression, and this situation isnoticed by a user, a row for that message's definition may be added tothe message table 1200.

The TELCORDIA ACTIVATOR® application may issue a command, which causesthe network to generate the response. When the response is received bythe network adapter framework, each regular expression (e.g., in themessage expression column 1204) in the message table 1200 is executed inorder to identify or isolate the unique message ID 1202 associated withthe response.

When invoked, the (?m)[MESSAGE] parameter used by each regularexpression in the message table 1200 indicates that a search should beperformed on all of the lines of the response, in order to find a stringthat matches [MESSAGE]. In some implementations, other notation otherthan (?m) may have other meaning, such as to parse messages in otherspecial ways. One purpose of the message table 1200, therefore, is todetermine the unique message ID 1202 associated with each particularresponse. The unique message ID 1202 is used in later steps ofprocessing.

If, based on performing the search using the (?m)[MESSAGE] regularexpression parameters listed in the message table 1200, a string in theresponse matches the [MESSAGE], the matching unique message ID 1202 isoutput. Alternatively, the message ID 1208 having the value MS_(—)031corresponding to the “.” regular expression parameter may be returnedwhen none of the strings of the response match any of the [MESSAGE]parameters of the regular expressions listed in the message expressioncolumn 1204 of the message table 1200. This indicates that the networkadapter framework has encountered an unknown response. Put another way,using the response as an input, the message table 1200 outputs a messageID 1202 associated with that response (e.g., message expression 1204).

The next configuration table, the command message table 1300 (FIG.13),uses both the message ID 1304 and the command ID 1302 to output amessage result type 1312, indicating whether the command was successfulor whether a fatal or non-fatal error occurred (e.g., based on themessage subtype 1310). The command message table 1300 also may output asuppress rollback indicator 1308, indicating whether the rollbackprocess should be suppressed or not (e.g., based on the suppressrollback indicator 1308).

If no rollback is to be performed and the command was successful, thenetwork adapter framework may allow another command to be processed,such as the next command in sequence. Furthermore, depending upon theparticular message ID 1304 and command ID1302, the command message table1300 can also output other parameters, such as the result code 1314,which may be used in later stages of processing or for the creation ofan output XML file.

In the following example of the use of regular expressions, theActivator application issues commands (e.g., using XML). Each commandmay include multiple discrete services, which are executed in sequence.The services and their sequence are identified using the service commandtable 1100, as discussed above.

Consider that the activator application 228 is performing the serviceCREATE. As shown in the service command table 1100, the CREATE servicemay be broken down into five separate steps or commands. For example,the steps may be: 1) LOGIN; 2) PORT DISABLE ADSL; 3) MODIFY PARAMETERSADSL; 4) ENABLE PORT ADSL; and 5) LOGOUT. Furthermore, the five commandsare to be executed in sequence, as shown by the command sequences 1106.

The first command (e.g., in this case, LOGIN) is sent by the frameworkto the network (e.g., using the Connection Manager adapter):

ACT-USER:7302-MR-01-   RJLLB07:SUPERUSER:   <INSERT_CTAG_HERE>::ANS#150;(1)

The above represents the LOGIN command of the CREATE service. Thiscommand is sent from the network adapter framework to the network.

7340035 2008-02-01 19:40:04 M 62 COMPLD  EN=0 ENDESC=Succeeded.; (2)

The above represents the formatted response to the LOGIN command of theCREATE service. This response is sent from the network to the networkadapter framework.

Referencing the regular expressions listed in the message table 1200,the term “Succeeded” is parsed from the above response, locating“Succeeded” on the third line of the response. Message ID “MS_(—)001”1212, corresponding to the term “Succeeded” 1214, is therefore output.

The known universe of possible message responses and their associatedmessage IDs are pre-configured in the message table 1200. If an unknownresponse is received, a default message ID may be used, which mighttrigger an error condition (and force a rollback). Additional messageIDs may be added to the message table 1200 at any time, such as to addthe definition for an “unknown” response.

The MS_(—)001 message ID 1304 and the CM_(—)001 command ID 1302 areinput to the command message table 1300. The subtype 1310 value of“Success,” the result type 1312 value of “SUCCESS” and result code 1314value of “0000” are output, indicating that the LOGIN command(CM_(—)001) was executed successfully. No rollback is performed (e.g.,the, suppress rollback indicator is “S”), and the next command isallowed to execute.

The next command, PORT DISABLE ADSL is then invoked:DACT-ADSLPORT::DEV=123,FN=0,SN=2,PN=321:63::;  (3)

The above represents the PORT DISABLE ADSL command of the CREATEservice. This command is sent from the network adapter framework to thenetwork.

7340035 2008-02-01 19:40:08 M 63 COMPLD  EN=0 ENDESC=Error processingthe command.  Invalid OSR.; (4)

The above represents the formatted response of the PORT DISABLE ADSLcommand of the CREATE service. This response is sent from the network tothe network adapter framework.

Referencing the regular expressions listed in the message table 1200,the term “Error processing the command. Invalid OSR.” is parsed from theabove response. The network adapter framework executes each of theregular expressions; however, none include a string which matches theresponse message.

Accordingly, the message ID MS_(—)031 1208 corresponding to the “.”regular expression parameter is returned since none of the strings ofthe response match any of the [message] parameters of the regularexpressions listed in the message table 1200. This indicates that thenetwork adapter framework has encountered an unknown response. The “.”regular expression parameter correlates to the “MS_(—)031” message ID.

The MS_(—)031 message ID 1304 and the CM_(—)002 command ID 1302 areinput to the command message table 1300 and, in the highlighted row1318, the subtype “Unknown error” 1320, result type 1312 value of “FATALERROR” and result code 1314 value of “AAFN-6106E” are output, indicatingthat the PORT DISABLE ADSL command (CM_(—)002) did not executesuccessfully.

Since the PORT DISABLE (CM_(—)002) command was not successful, and thesuppress rollback indicator is “N”, rollback is performed. Ashighlighted in the service command table 1100, the rollback processassociated with the CREATE command (SV_(—)001) and the PORT DISABLE ADSLcommand (CM_(—)002) is rollback service process SV_(—)006 1134. Thisrollback process may or may not be disabled based on the enable rollbackindicator 1110 of the service command table 1100.

Messages and processing used in the network adapter framework mayinclude the use of XML files. For example, the Activator applicationissues commands to the network. The network processes the commands, andgenerates a response. The network adapter framework receives thisresponse from the network, and may generate an XML file. The XML file issent back to the Activator application as the result of the commandwhich it issued earlier. Once the XML file is received, the activatorcan parse the XML and use the information collected to continue this orother processes. The XML file can be stored in the activator database,or in a directory, or by other means, depending on the implementation.The information included can be useful for the user of the client,because the user can read the details of the results of the activationmade in the network by the adapters.

Depending upon the response from the network, the XML file may includedifferent information, in various formats. The different information andformats may be generically represented using GADE variables in anadditional configuration table, as shown in the return messageexpression column 1406 of the return message table 1400. As mentionedpreviously, GADE variables are substitution variables embedded in returnmessages. The GADE variables are replaced with actual values, dependingon various factors. The content and format of the XML file may bealtered by changing the content and format of the GADE variables.

For example, the row 1408 in the return message table 1400 defines theentry for a return message code MR_(—)002 1410. A corresponding returnmessage description 1412 describes the message as “Message of Erroroutput—Huawei”. GADE variables for the message are included in thereturn message expression cell 1414 containing“[:&RESULT_CODE:]:[:&RESULT_TYPE:] . . . ” The first GADE variable is“[:&RESULT_CODE:]” and the second is [:&RESULT_TYPE:]. As is common withreturn messages containing GADE variables, other characters andpunctuation may also exist, such as the colon (“:”) between the two GADEvariables.

The response generated by the network (for example, in response to aCreate, Delete, or Suspend service or a LOGIN command), includesinformation which is used to populate the GADE variables, therebycreating the XML file. In some implementations, the return message table1400 cannot accommodate new variables unless deeper changes to theunderlying software class (e.g., JAVA class) are made. However, any newvariables are defined once, and thereafter are used (and re-used)multiple times as needed.

If an error is detected during the process, the information derived fromthe configuration tables may be used to populate an XML return message.The variables and their associated data sources are described below.

The returned message, before GADE variable substitution, may be, forexample:

[:&RESULT_CODE:]:[:&RESULT_SUBTYPE:]- [[:&SEQ_COMMAND:]/[:&QTY_COMMAND:]]:[:&OPERATION_NAME:]-[:&SERVICE_TYPE_NAME:]:[:&TECHNOLOGY_TYPE_NAME:]-[:&TECHNOLOGY_NAME:]-[:&DEVICE_MODEL:]-DEVICE_NAME=[:#ACT_HUAWEI_DEVICE_NAME:]-RACK=[:#ACT_HUAWEI_RACK:]-SHELF= [:#ACT_(—) HUAWEI_SHELF:] -SLOT=[:#ACT_HUAWEI_SLOT:] -PORT= [:#ACT_(—) HUAWEI _PORT:] (5)

During the process, GADE variables are filled with data values, asdescribed in the following:

[:&RESULT_CODE:] = result code of the process [:&RESULT_SUBTYPE:] =subtype of the result [:&SEQ_COMMAND:] = sequential of the command[:&QTY_COMMAND:] = quantity of the commands executed in the network[:&OPERATION_NAME:] = the name of the service [:&SERVICE_TYPE_NAME:] =type of service [:&TECHNOLOGY_TYPE_NAME:] = the technology type[:&TECHNOLOGY_NAME:] = the technology name [:&DEVICE_MODEL:] = modeldevice [:#ACT_HUAWEI_DEVICE_NAME:] = the device name[:#ACT_HUAWEI_RACK:] = rack of device [:#ACT_HUAWEI_SHELF:] = shelf ofdevice [:#ACT_HUAWEI_SLOT:] = slot of device [:#ACT_HUAWEI_PORT:] = portof device (6)

After filling in GADE variable values in the XML, the result may be:

0000:ERROR-[1/2]:CREATE-ADSL_BB:DSLAM-HUAWEI-TL1- ISAM 7302XD-DEVICE_NAME=RJ-IPA05-EDSLAM-RACK=01-SHELF= 1-SLOT=06-PORT=44 (7)

FIG. 15 shows an example translation of GADE variables into actualvalues in a return message. For example, the translation may translate amessage response with GADE variables 1502 into a message response aftersubstitution 1504. The translation may be performed, for example, by aGADE variable substitution module 1506 using one or more configurationtables or other processes, as described above. As a result, in oneexample substitution, a GADE variable [:&RESULT_CODE:] 1508 may bereplaced by a value AAFN-6106E 1510. In another example substitution, aGADE variable [:&OPERATION_NAME:] 1512 may be replaced with a valueCREATE 1514. The following provides a more detailed discussion of theGADE variable substitution process.

When the adapter is activated, it may load the data of configurationfiles (e.g., using <ADAPTER _(—) NAME>ADAPTERCONFIGURATION.XML). Duringthis process, the GADE variables may be initialized with valuesconfigured in one or more parameter tables. When a request (e.g., viaJMS messages) is posted in the adapter queue, the framework may processthe request file and initialize another sets of GADE variables (e.g., byreading the XML stored in the variables).

For example, the following set of values, (e.g., stored in a parametertable) may be used to load the corresponding Huawei adapter variables:

ACT_HUHUAWEI_DEVICE_NAME= ALPJ_-EHA201 ACT_HUHUAWEI_SHELF=0ACT_HUHUAWEI_SLOT=11 ACT_HUHUAWEI_PORT=14 (8)

Such values in the parameter tables may show the association of GADEvariables with the XML path.

The example that follows describes GADE variable substitution that mayoccur for a PORT DISABLE ADSL HUAWEI service. After processing the XMLfile and defining the service that will be executed, the framework: 1)loads the network commands for the service (refer to the service commandtable 1100); and 2) associates the values read from XML with thecorresponding GADE variables.

For each command or service, a message result containing GADE variablesmay exist, such as:

DACT- ADSLPORT::DEV=[:#ACT_HUAWEI_DEVICE_NAME:],FN=[:#ACT_HUAWEI_SHELF:],SN=[:#ACT_HUAWEI_SLOT:],PN=[:#ACT_HUAWEI_PORT:]:<INSERT_CTAG_HERE>::; (9)

Based in the values stored for the variables (e.g., in the parametertable), the framework may execute the appropriate substitution, formingthe command, such as:DACT-ADSLPORT::DEV=ALPJ_-EHA201,FN=0,SN=11,PN=14:2343::;  (10)

The framework sends the command to the communication module (e.g., theconnection manager), that sends the message to the network, which inturn may return the response, such as:

7344401 2009-01-29 23:08:56 M 121802 COMPLD  EN=0 ENDESC=Succeeded. ;](11)

Using regular expressions, the framework may match the network responsewith each previously-registered response (e.g., in the message table1200).

If a match occurs, the framework may execute the process configured forthat kind of response (e.g., using the command message table 1300).Based in the message ID column 1202 in the message table 1200, theframework may verify the relationship (e.g., Hibernate) with the commandmessage table 1300, getting the next process to be executed. In a caseof an error, the next process may be a rollback command.

Assuming that the network answer indicates success, the next command maybe loaded and processed in the same way.

Next, the framework may load the next command (MODIFY PARAMETERS ADSLHUAWEI):

MOD- ADSLPORT::DEV=[:#ACT_HUAWEI_DEVICE_NAME:],FN=[:#ACT_HUAWEI_SHELF:],SN=[:#ACT_HUAWEI_SLOT:], PN=[:#ACT_HUAWEI_PORT:]:<INSERT_CTAG_HERE>::LPROFID=[:#ACT_HUAWEI_PRIMARY_PROFILE:],ALIAS= [:#ACT_HUAWEI_ALIAS:]; (12)

Substituting the GADE variables, the next command may be built:

MOD-ADSLPORT::DEV=ALPJ_-EHA201,FN=0,SN=11,PN=14:4323::LPROFID=VELOX1000GDMT, ALIAS=MCOAD5077916;(13)

After the command is sent to the network, a response may be received,such as:

7344401 2009-01-29 23:08:57 M 121803 COMPLD  EN=0 ENDESC=Succeeded. ;]ACT-ADSLPORT::DEV=ALPJ_-EHA201,FN=0,SN= 11,pN=14:121804::; 73444012009-01-29 23:08:57 M 121804 COMPLD  EN=0 ENDESC=Succeeded. ;] (14)

After processing all the commands of the service, the GADE variables aregenerated with values of the process, allowing the framework to generateand send the fully-qualified response to the owner of the request. Asshown in the return message table 1400, different types of responses mayexist, one for each kind of situation. To find the correct XML answer,the adapter may use a return message (e.g., from a response table orfrom the return message column of the return message table 1400.)

The framework may fill in the XML with the GADE values and send amessage (with the generated XML) to the queue. At this moment, all GADEvariables are “clean” (e.g., translated into actual values)

For example, a response originally containing un-substituted GADEvariables may be:

<NetworkResponse> [:&RESULT_CODE:]:[:&RESULT_SUBTYPE:]-[[:&SEQ_COMMAND:]/ [:&QTY_COMMAND:]]:[:&OPERATION_NAME:]-[:&SERVICE_TYPE_NAME:]:[:&TECHNOLOGY_TYPE_NAME:]-[:&TECHNOLOGY_NAME:]-[:&DEVICE_MODEL:]-DEVICE_NAME=[:#ACT_HUAWEI_DEVICE_NAME:]-SHELF=[:#ACT_HUAWEI_SHELF:]-SLOT= [:#ACT_HUAWEI_SLOT:]-PORT=[:#ACT_HUAWEI_PORT:] </NetworkResponse> (15)

As a result of substitution, the XML response generated may be:

<NetworkResponse> <![CDATA[AAFN-6106E:SUCCESS-Port Modify:[3/3]:CREATE-ADSL_BB:DSLAM -HUAWEI-FSAP 9800-DEVICE_NAME= ALPJ_-EHA201-SHELF=14-SLOT=11-PORT=14]]></ErrorText> </ NetworkResponse > (16)

The framework described herein may be configured to use GADE variables.GADE variables were developed to assist the enhanced framework toconfiguring an adapter, and the variables serve as a customized languagethat is specific to the enhanced framework. The language can be used toconfigure the network commands and responses in the configuration tablesor other tables in the framework.

The GADE variable is a language component of regular expressions withterms defined specifically to an adapter. The terms can be defined, forexample, in the following language POSIX standard syntax. An expressionis initiated by an open bracket followed by a colon (e.g., “[:”). Anexpression is terminated by a colon followed by a closing bracket (e.g.,“:]”). The first character (e.g., “$”, “&”, etc.) of a GADE variable candenote the meaning of the term, as will now be described.

A GADE variable starting with a dollar sign and used as a directreference to a variable can have the format [:$<path>:]. In this case,the regular expression <path> can be replaced with the parameter that isto be used.

A GADE variable starting with a pound symbol and used as an indirectreference to a variable can have the format [:#<name>:]. In this case,the regular expression <name> can be replaced with the name of theparameter that is to be used.

A GADE variable starting with an “amperes and” and used simply as a GADEvariable can have the format [:@<name>:]. In this case, the frameworkcan access the value of the variable previously declared and initialized(e.g., “Definition of variable . . . ”).

A GADE variable starting with “&” and used as an environment variablecan have the format [:&<name>:]. In this case, the framework can accessthe value of the environment variable, for example UUID (e.g., for64-bit identifiers), SEQ (sequential number generated for each command),and ROLLBACK (result of processing: Y=success; N=Failure).

A GADE variable used as the first position of an array can have theformat [:@ name$:]. In this case, the variable can be used to access thevalue of the first position of a variable array.

A GADE variable used as a position of an array can have the format [:@name$(1):]. In this case, the variable can be used to access the valueof any position of the variable array. The desired position is indicatedwith parentheses, where the first position can be zero (typically) orone.

A GADE variable used as an array size can have the format [:@name$qty:]. In this case, the variable can be used to identify thenumber of values in the array, or the available space in the array.

In general, GADE variables and expressions can determine variouscharacteristics of adapters in the framework. For example, GADEvariables can reference an external value set by the adapter andjavabean, such as an adapter request (e.g., “AdapterRequest”) identifiedwith the dollar (“$”) character. GADE variables can also provide analias or name that represents a parameter set in the parameter table.Also, GADE variables can be used in the initialization of environmentvariables within the context of implementation of the adapter. Finally,GADE variables can provide reference to a variable initialized withinthe context of the implementation of the adapter.

In one example of an expression using GADE variables, such as in an“AdapterRequest,” the expression can be similar to the following:

LOGIN:::EQ=[:#equip_id:]::UN=[:#username:],PWD=[:#password:],  GROUP=[:#default-group:] (17)

FIG. 16 is a block diagram of computing devices 1600, 1650 that may beused to implement the enhanced network adapter framework, as either aclient or as a server or plurality of servers. Computing device 1600 isintended to represent various forms of digital computers, such aslaptops, desktops, workstations, personal digital assistants, servers,blade servers, mainframes, and other appropriate computers. Computingdevice 1650 is intended to represent various forms of mobile devices,such as personal digital assistants, cellular telephones, smartphones,and other similar computing devices. The components shown here, theirconnections and relationships, and their functions, are meant to beexemplary only, and are not meant to limit implementations describedand/or claimed in this document.

Computing device 1600 includes a processor 1602, memory 1604, a storagedevice 1606, a high-speed interface 1608 connecting to memory 1604 andhigh-speed expansion ports 1610, and a low speed interface 1612connecting to low speed bus 1614 and storage device 1606. Each of thecomponents 1602, 1604, 1606, 1608, 1610, and 1612, are interconnectedusing various busses, and may be mounted on a common motherboard or inother manners as appropriate. The processor 1602 may processinstructions for execution within the computing device 1600, includinginstructions stored in the memory 1604 or on the storage device 1606 todisplay graphical information for a GUI on an external input/outputdevice, such as display 1616 coupled to high speed interface 1608. Inother implementations, multiple processors and/or multiple buses may beused, as appropriate, along with multiple memories and types of memory.Also, multiple computing devices 1600 may be connected, with each deviceproviding portions of the necessary operations (e.g., as a server bank,a group of blade servers, or a multi-processor system).

The memory 1604 stores information within the computing device 1600. Inone implementation, the memory 1604 is a computer-readable medium. Inone implementation, the memory 1604 is a volatile memory unit or units.In another implementation, the memory 1604 is a non-volatile memory unitor units.

The storage device 1606 is capable of providing mass storage for thecomputing device 1600. In one implementation, the storage device 1606 isa computer-readable medium. In various different implementations, thestorage device 1606 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device, a flash memory or other similarsolid state memory device, or an array of devices, including devices ina storage area network or other configurations. In one implementation, acomputer program product is tangibly embodied in an information carrier.The computer program product contains instructions that, when executed,perform one or more methods, such as those described above. Theinformation carrier is a computer- or machine-readable medium, such asthe memory 1604, the storage device 1606, or memory on processor 1602.

The high speed controller 1608 manages bandwidth-intensive operationsfor the computing device 1600, while the low speed controller 1612manages lower bandwidth-intensive operations. Such allocation of dutiesis exemplary only. In one implementation, the high-speed controller 1608is coupled to memory 1604, display 1616 (e.g., through a graphicsprocessor or accelerator), and to high-speed expansion ports 1610, whichmay accept various expansion cards (not shown). In the implementation,low-speed controller 1612 is coupled to storage device 1606 andlow-speed expansion port 1614. The low-speed expansion port, which mayinclude various communication ports (e.g., USB, Bluetooth, Ethernet,wireless Ethernet) may be coupled to one or more input/output devices,such as a keyboard, a pointing device, a scanner, or a networking devicesuch as a switch or router, e.g., through a network adapter.

The computing device 1600 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 1620, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 1624. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 1622. Alternatively, components from computing device 1600 maybe combined with other components in a mobile device (not shown), suchas device 1650. Each of such devices may contain one or more ofcomputing device 1600, 1650, and an entire system may be made up ofmultiple computing devices 1600, 1650 communicating with each other.

Computing device 1650 includes a processor 1652, memory 1664, aninput/output device such as a display 1654, a communication interface1666, and a transceiver 1668, among other components. The device 1650may also be provided with a storage device, such as a microdrive orother device, to provide additional storage. Each of the components1650, 1652, 1664, 1654, 1666, and 1668, are interconnected using variousbuses, and several of the components may be mounted on a commonmotherboard or in other manners as appropriate.

The processor 1652 may process instructions for execution within thecomputing device 1650, including instructions stored in the memory 1664.The processor may also include separate analog and digital processors.The processor may provide, for example, for coordination of the othercomponents of the device 1650, such as control of user interfaces,applications run by device 1650, and wireless communication by device1650.

Processor 1652 may communicate with a user through control interface1658 and display interface 1656 coupled to a display 1654. The display1654 may be, for example, a TFT LCD display or an OLED display, or otherappropriate display technology. The display interface 1656 may compriseappropriate circuitry for driving the display 1654 to present graphicaland other information to a user. The control interface 1658 may receivecommands from a user and convert them for submission to the processor1652. In addition, an external interface 1662 may be provide incommunication with processor 1652, so as to enable near areacommunication of device 1650 with other devices. External interface 1662may provide, for example, for wired communication (e.g., via a dockingprocedure) or for wireless communication (e.g., via Bluetooth or othersuch technologies).

The memory 1664 stores information within the computing device 1650. Inone implementation, the memory 1664 is a computer-readable medium. Inone implementation, the memory 1664 is a volatile memory unit or units.In another implementation, the memory 1664 is a non-volatile memory unitor units. Expansion memory 1674 may also be provided and connected todevice 1650 through expansion interface 1672, which may include, forexample, a SIMM card interface. Such expansion memory 1674 may provideextra storage space for device 1650, or may also store applications orother information for device 1650. Specifically, expansion memory 1674may include instructions to carry out or supplement the processesdescribed above, and may include secure information also. Thus, forexample, expansion memory 1674 may be provide as a security module fordevice 1650, and may be programmed with instructions that permit secureuse of device 1650. In addition, secure applications may be provided viathe SIMM cards, along with additional information, such as placingidentifying information on the SIMM card in a non-hackable manner.

The memory may include for example, flash memory and/or MRAM memory, asdiscussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 1664, expansionmemory 1674, or memory on processor 1652.

Device 1650 may communicate wirelessly through communication interface1666, which may include digital signal processing circuitry wherenecessary. Communication interface 1666 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 1668. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS receiver module 1670 may provide additional wireless datato device 1650, which may be used as appropriate by applications runningon device 1650.

Device 1650 may also communication audibly using audio codec 1660, whichmay receive spoken information from a user and convert it to usabledigital information. Audio codex 1660 may likewise generate audiblesound for a user, such as through a speaker, e.g., in a handset ofdevice 1650. Such sound may include sound from voice telephone calls,may include recorded sound (e.g., voice messages, music files, etc.) andmay also include sound generated by applications operating on device1650.

The computing device 1650 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 1680. It may also be implemented as part of asmartphone 1682, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here maybe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and may be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions. Although the use of JAVA codeand Telcordia Activator software is discussed herein, this disclosureinvention is not limited to any particular software or languageimplementation.

To provide for interaction with a user, the systems and techniquesdescribed here may be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user may provideinput to the computer. Other kinds of devices may be used to provide forinteraction with a user as well; for example, feedback provided to theuser may be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user may bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here may be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usermay interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system may be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. Accordingly, otherimplementations are within the scope of the following claims.

1. A computer-implemented method comprising: storing parameters in oneor more configuration tables, the parameters being customized for anetwork and an application; instantiating a network adapter customizedfor the network and the application based on invoking a generic networkadapter which externally references the parameters stored in the one ormore configuration tables; and effecting communication between theapplication and the network using the instantiated network adapter,wherein effecting communication between the application and the networkusing the instantiated network adapter further comprises: receiving arequest from the application to perform a service on the network,identifying commands and a sequence of the commands associated with theservice based on referencing a unique identifier of the service in afirst configuration table, transmitting at least two commands, in anorder specified by the sequence of the commands, to the network,receiving a response to at least one of the commands from the network,identifying a unique message identifier associated with the responsebased on executing regular expressions listed in a second configurationtable, and determining an outcome of the at least one command based onreferencing the unique message identifier associated with the responseand a unique identifier of the command in a third configuration table.2. The method of claim 1, wherein effecting communication between theapplication and the network using the instantiated network adapterfurther comprises: determining an outcome of the service based ondetermining outcomes of all commands associated with the service;selecting an XML return message, including General Adapter DeclarativeExpression (GADE) variables, based on referencing the outcome of theservice in a fourth configuration table; populating the GADE variablesusing one or more result values associated with the outcomes of allcommands associated with the service; and providing the XML returnmessage, populated with result values, to the application.
 3. The methodof claim 1, wherein the service is selected from the group consisting ofan ADSL port disable service, an ADSL modify parameters service, or anADSL enable port service.
 4. The method of claim 1, further wherein theregular expressions for each possible response to the command are listedwith associated unique message identifiers in the second configurationtable.
 5. The method of claim 4, wherein the second configuration tablelists a catch-all regular expression for all previously unknown orunidentified responses sent by the network, and a unique messageidentifier for the catch-all regular expression.
 6. The method of claim1, wherein the outcome identifies whether the at least one command wassuccessful or whether a fatal or non-fatal error has occurred, andwhether rollback is suppressed or not suppressed.
 7. The method of claim6, wherein the outcome further identifies a result value.
 8. The methodof claim 1, wherein the application comprises a TELCORDIA® ACTIVATORapplication.
 9. The method of claim 1, wherein the generic networkadapter comprises a JAVA EE-based network adapter.
 10. The method ofclaim 1, wherein the parameters comprise values for rules implementingprocess flows.
 11. The method of claim 1, wherein the parameterscomprise responses expressed as regular expressions.
 12. The method ofclaim 1, wherein the parameters comprise commands capable of being sentfrom the application to the network, or responses to the commandscapable of being sent from the network to the application.
 13. Themethod of claim 1, further comprising invoking the generic adapter usinga single configuration load of the one or more configuration tables. 14.The method of claim 1, further comprising: detecting a type of thenetwork and the application; and selecting the one or more configurationtables from among a plurality of configuration tables based on thedetected type of the network and the application.
 15. The method ofclaim 1, wherein the parameters comprise actions associated with aloopback mode, a network emulator mode, and a network mode.
 16. Themethod of claim 1, wherein the parameters comprise service definitions.17. A system comprising: one or more computers; and a computer-readablemedium coupled to the one or more computers having instructions storedthereon which, when executed by the one or more computers, cause the oneor more computers to perform operations comprising: storing parametersin one or more configuration tables, the parameters being customized fora network and an application, instantiating a network adapter customizedfor the network and the application based on invoking a generic networkadapter which externally references the parameters stored in the one ormore configuration tables, and effecting communication between theapplication and the network using the instantiated network adapter,wherein effecting communication between the application and the networkusing the instantiated network adapter further comprises: receiving arequest from the application to perform a service on the network,identifying commands and a sequence of the commands associated with theservice based on referencing a unique identifier of the service in afirst configuration table, transmitting at least two commands, in anorder specified by the sequence of the commands, to the network,receiving a response to at least one of the commands from the network,identifying a unique message identifier associated with the responsebased on executing regular expressions listed in a second configurationtable, and determining an outcome of the at least one command based onreferencing the unique message identifier associated with the responseand a unique identifier of the command in a third configuration table.18. A non-transitory computer storage medium encoded with a computerprogram, the program comprising instructions that when executed by dataprocessing apparatus cause the data processing apparatus to performoperations comprising: storing parameters in one or more configurationtables, the parameters being customized for a network and anapplication; instantiating a network adapter customized for the networkand the application based on invoking a generic network adapter whichexternally references the parameters stored in the one or moreconfiguration tables; and effecting communication between theapplication and the network using the instantiated network adapterwherein effecting communication between the application and the networkusing the instantiated network adapter further comprises: receiving arequest from the application to perform a service on the network,identifying commands and a sequence of the commands associated with theservice based on referencing a unique identifier of the service in afirst configuration table, transmitting at least two commands, in anorder specified by the sequence of the commands, to the network,receiving a response to at least one of the commands from the network,identifying a unique message identifier associated with the responsebased on executing regular expressions listed in a second configurationtable, and determining an outcome of the at least one command based onreferencing the unique message identifier associated with the responseand a unique identifier of the command in a third configuration table.